HotJava Installation Instructions, Microsoft Windows NT (Intel) and Windows 95

The HotJava Browser 1.0 win32 release supports only Microsoft Windows NT/Intel and Windows 95.

The HotJava Browser 1.0 does not run on Windows 3.1 or 3.11.

HotJava Browser 1.0 now comes bundled with the Java Runtime Environment (JRE) and does not require a separate Java Development Kit (JDK) installed on your computer.

HotJava Browser 1.0 is delivered in an installation program to handle the details of installing the HotJava Browser 1.0 on your computer. The program makes the necessary modification to your computer's PATH enviroment variable as well as the installation of the HotJava Browser 1.0 files.

If you experience trouble along the way, check the Troubleshooting section.

Step 1: Copy the HotJava Browser 1.0 installation program

Click here to copy the HotJava Browser 1.0 installation program to your system

Step 2: Run the HotJava Browser 1.0 installation program

After copying, run the HotJava Browser 1.0 installation program by double clicking on its icon.

hjb1_0wg.exe

Alternatively, run the HotJava Browser by typing its name in a Command Prompt window (available under Programs from the Start menu):

C:\>hjb1_0wg.exe

This will create a HotJava parent directory and all of the necessary subdirectories and files for this release, including lib\classes.zip. DO NOT UNZIP THE CLASSES.ZIP FILE.

You need to log out and log back in before you can run HotJava Browser 1.0

Step 3: Run HotJava Browser 1.0

The easist way to run HotJava Browser 1.0 is from the Start Menu. Click on Start, go to Programs then HotJava Browser and choose HotJava Browser.

You can also start the HotJava Browser running by double clicking on the:

hotjava

icon in:

C:\HotJava\bin
(This assumes you used the default installation location. If you installed into a different location, click on the icon there.)

Or, you can start the HotJava Browser by typing from a Command Prompt window (available under Programs from the Start menu):

C:\HotJava\bin\hotjava.exe
(Again, this assumes you used the default installation location. If not, start the program from the location in which you installed it.)

You can also create a program item, or shortcut if running Windows 95, containing a link to the executable so that HotJava can be started directly from the desktop by double-clicking the HotJava icon.

Troubleshooting

If you are running HotJava under Windows ('95 or NT), and you have another version of the JDK installed, you might run into this problem. When you attempt to launch HotJava, it will fail with the error message:
```
[Starting HotJava] Unable to initialize threads: cannot find class
  java/lang/Thread 
```
Or it may fail with an error message like this:
```
[Starting HotJava] [Initializing globals] [Creating frame] java.lang.UnsatisfiedLinkError:
  getClassContext at java.util.ResourceBundle.getLoader(ResourceBundle.java:320)
  at java.util.ResourceBundle.getBundle(ResourceBundle.java:311) at java.util.Calendar.setWeekCountData(Calendar.java:831)
  ... 
```
There are two reasons this might be happening:
1) You're picking up .class files from another JDK, because you have either the JDK_HOME or JRE_HOME environment variable pointing at another JDK.
To work around the this problem, make sure that neither the JDK_HOME nor JRE_HOME environment variable is set.
2)You're getting .dll's from another JDK, because that JDK appears on your path before the HotJava\runtime\bin directory.
The work around for this problem is to copy all of the .dll files from the HotJava\runtime\bin directory into the HotJava\bin directory. For example, if you installed HotJava in its default location of c:\HotJava, you can enter this command from a DOS prompt:
```
copy c:\HotJava\runtime\bin\*.dll
  c:\HotJava\bin 
```
If you see the following error message
```
net.socketException: errno
  = 10047 OR Unsupported version of Windows Socket API 
```
check which TCP/IP drivers you have installed. The HotJava Browser only supports the Microsoft TCP/IP drivers included with Windows 95 and Windows NT. If you are using third-party drivers (e.g., Trumpet Winsock), you'll need to change over to the native Microsoft TCP/IP drivers if you want to load applets over the network.